@REM XHelvetica is allowed too ;), why is there no @sysfont 1?
@WORDWRAP
@NODE Main "BrowserII V3.0 Documentation"
@{JCENTER}
Welcome to
@{u} @{B2} @{uu}
The @{i}other@{ui} file manager!
Version 3.09
Copyright
1991-94
Pierre CARRETTE & Sylvain ROUGIER
Icons & Graphics by Walter D
rwald
Guide by P.C, by S.R starting from 3.03
@{CODE}@{u} @{uu}@{BODY}
@{JLEFT}@{SETTABS 48}@{LINDENT 6}
@{" Read this first! " Link "Read this first"}
@{" System requirements " Link "System requirements"}
@{" Installation " Link "Install"}
@{" Introduction " Link "Introduction"} Start reading this.
@{" Features " Link "Features"} Most important features
@{" The history " Link "History"} Why did we rewrite the original Browser?@{END1}
@{CHAP1 "Using @{B2}"}
@{" Running BrowserII " Link "Running"} Tooltypes and WBStartup drawer support.
@{" Basic knowledge " Link "BasicKnowledge"} You @{b}must@{ub} know that.
@{" Common problems " Link "CommonProblems"} Frequently asked questions.
@{" Directory trees " Link "Tree"} Opening and using tree windows.
@{" Archive Support " Link "ArchiveSupport"} Displaying archive contents.
@{" Zooming windows " Link "Zoom"} Maximize window size.
@{" Snapshotting windows " Link "Snapshots"} Saving window properties.
@{" Iconify " Link "Iconify"} How iconification works in @{B2}.
@{" Network/Multiuser " Link "Network"} Network and MultiuserFS support.
@{" Standard Menus " Link "Menus"} Builtin menus usage.
@{" Mouse and Keyboard " Link "Keyboard"} Summarize important keys/qualifiers.
@{" Jauges " Link "Jauges"} Windows' jauges usage.
@{" Select Requester " Link "SelectRequester"} Criteria file selection/filtering.
@{" FileExist Requester " Link "FileExistsRequester"} Important and often used requester.
@{" Commodity " Link "Commodity"} Popping up @{B2} with a hotkey.
@{" Workbench Support " Link "WorkbenchSupport"} AppIcon & AppWindows.
@{" External Command BD " Link "ExternalCommandBD"} Opens dirs from a shell.@{END1}
@{CHAP1 "Configuration"}
@{" User Menus " Link "BrowserII.menu"} Creating user menus.
@{" Command Hot keys " Link "CmdHotKeys"} Running commands by hot keys.
@{" Auto Commands " Link "AutoCmds"} Commands associated to File Types.
@{" File Types " Link "whatis.library"} Creating new File Types.@{END1}
@{CHAP1 "Miscellaneous"}
@{" Changes since v2.x " Link "Changes"} v2.x users @{b}must@{ub} read this.
@{" Release Notes " Link "Release Notes"} Features history since v1.0.
@{" Future Plans " Link "Future Plans"} What will be the next versions...
@{" Getting Updates " Link "Updates"} Where and how to get new versions.
@{" Copyright " Link "Copyright"} Pierre CARRETTE & Sylvain ROUGIER!
@{" Registration " Link "Registration"} Why registering and how.
@{" Bug reports " Link "Bug reports"} Found some bugs?
@{" Acknowledgements " Link "Acknowledgements"} We wish to thank...
@{" Disclaimer " Link "Disclaimer"} Be warned!
@ENDNODE
@NODE "Read this first" "BrowserII.guide/Read this first"
@{START}
@{CHAP1 "Please read this"}
Please, even if you hate reading documentations, read at least the following pages, @{" Introduction " Link Introduction}, @{" Features " link Features} and @{" Basic knowledge " link BasicKnowledge} or you will miss some important things in @{B2}. These chapters are small. It will take you just a few minutes to read them.
For users of @{B2} v2.x, read important @{" Changes " link Changes} from v2.x to v3.0.
@{B2} requires version 2.0 of the Amiga operating system or higher. To get a full featured @{B2}, you should also install the @{" whatis.library " link "whatis.library"}, and the @{" ObjectArchive " link ArchiveSupport} package.
@ENDNODE
@NODE Install "BrowserII.guide/Install"
@{START}
@{CHAP1 "Installation"}
@{B2} is distributed together with an Installer script, therefore making installation a breeze! Just doubleclick on the
Install-BrowserII
icon and the installation procedure is on its way.
@ENDNODE
@NODE Introduction "BrowserII.guide/Introduction"
@{START}
@{CHAP1 "Introduction"}
@{B2} is a multi-window file manager, i.e. it is not limited to two scrolling lists! This also means that you can see @{b}all@{ub} informations about a file (several files), size, date, time, protection, file type, comment, ... without horizontal scrolling! No need to select a file to follow it horizontally!
It works like Workbench. Copy files by dragging and dropping them over the destination directory.
But @{B2} is not only a usual file manager. Most people use both a shell and a file manager depending on the work they are doing. @{B2} is also a tool making life easier in a shell-like environment.
Where to you spend most of your time in a shell? Typing file names? You think that filename completion is the best help? @{b}You are wrong!@{ub} Imagine that @{B2} is a shell. In each window, you have a directory displayed, so that all files are immediately selectable. You then want to execute a command in one of these.
In a shell, what would you do? Change the current dir, by CD'ing several times? How long does it take?
Now consider your directory is here, just in front of you. Activate the window, your
is done. Select the desired file(s), and then press the
key. A requester appears asking you to complete the command. Press return... Quick, no?
Even better: You use some commands quite often? Create a menu with a shortcut or a more sophisticated hotkey. Select the files, press your hotkey, et voil
For example, I have
BumpRev
Indent
, ... menus, making my development environment a dream! I can work on different development directories at the same time, without typing even a single shell command! See the last menu named
of my @{" BrowserII.menu " link //BrowserII.menu-example/Main} configuration file subset.
As a last word for this introduction, know that we use @{B2} all the time, for every thing. We (Sylvain and I) even don't load Workbench at boot time! Funny isn't it? ;-) That's why one of the next @{B2} features will be icon display, the only reason why we (sometimes!) run Workbench.
See the @{" Features " link Features} page for a complete detailed list of features.
@ENDNODE
@NODE Features "BrowserII.guide/Features"
@{START}
@{CHAP1 "Features"}
Some features of @{B2} makes it a different and powerful file manager.
@{SUB2 "
"}Asynchronous operations:
Several (unlimited) operations can be performed at the same time. Copying files, deleting others, running tools, scanning directories, all at the same time!@{END2}
@{SUB2 "
"}Directory trees:
@{B2} has a finder-like @{" directory tree " link Tree}. Examine the whole contents of a floppy disk by just a double click!@{END2}
@{SUB2 "
"}Powerful copy and other DOS operations@{END2}
@{SUB2 "
"}Networking:
@{B2} has a full @{" Network/MultiuserFileSystem " link Network} support.@{END2}
@{SUB2 "
"}Archive support:
It has the most powerful @{" archive support " link ArchiveSupport} using the @{OA} system.@{END2}
@{SUB2 "
"}Hard and soft links support@{END2}
@{SUB2 "
"}Proportional font support allowing to nicely display lots of informations about files in less space.@{END2}
@{SUB2 "
"}Device list with volume statistics@{END2}
@{SUB2 "
"}And it is small. About 150 KBytes including its libraries.@{END2}
@ENDNODE
@NODE "History" "BrowserII.guide/History"
@{START}
@{CHAP1 "History"}
We wrote @{B2} after having used the original Browser (version 1.6a) written by Peter Da Silva for two years. We were not fully satisfied because of some of its limitations so, as soon as we felt capable of writing a program which would overcome those limitations, we made a decision to do it. So @{B2} was born... The Return!
We felt the overall layout and display mode of Browser were very good, so we decided to keep them, as well as the name, so that actual users of Browser would immediately feel at home with @{B2}.
As we never had the sources of Browser at hand, we rewrote it from scratch.
A few months ago, I had a chat with Peter, who discovered our piece of work. It was really exciting to speak (by email) with our spiritual father ;-) So, if you read this, Hello Peter!
@ENDNODE
@NODE Running "BrowserII.guide/Running BrowserII"
@{START}
@{CHAP1 "Running @{B2}"}
@{B2} can of course be run just like any other tool. But you should take care to run it from an environment that makes it inherit your default shell path, so that it can run commands without problems.
It can also be run through the separate @{" BD " link ExternalCommandBD} command.
If you want to start @{B2} from your WBStartup drawer, you may create a project icon with the default tool set to
BrowserII
if @{B2} is in your path, or to the full path to @{B2}. The installation procedure will do it for you if you want.
There are some optional tooltypes:
@{SUB2 "
"}APPICON
default is "BrowserII"@{END2}
@{SUB2 "
"}ICONXPOS
default is
NOICONPOSITION
@{END2}
@{SUB2 "
"}ICONYPOS
default is
NOICONPOSITION
@{END2}
If you set APPICON=NONE, the only way to uniconify @{B2} is to use the @{" hotkey " link Commodity} or Commodities Exchange utility. See @{" Commodity " link Commodity} for other tooltypes.
First of all, you should read the @{" Introduction " link Introduction} chapter.
When you first start @{B2}, you get just a simple window, called the @{b}Main@{ub} window, which contains the DOS device list, i.e. by default, the list of mounted volumes and assigns. To adapt the contents of this window, use the BrowserII/@{" Device List " link DeviceListSub} submenu.@{END2}
@{CHAP2 "Window bottom border informations"}
@{SUB3 "
"}Main window
When the active window is a directory or @{" tree " link Tree}, volume informations appear in the bottom border of the main window. If the volume is write protected, thoses informations appear in italic.
If the main or alien window is active, the bottom border of the main window contains the statistics about selected files.@{END3}
@{SUB3 "
"}Directories/Trees
In the bottom border of windows appear:@{END4}
@{SUB4 "
"}If no entries are selected
The total statistics about window contents@{END4}
@{SUB4 "
"}If some entries are selected
The selection statistics for that window@{END3}
@{B2} makes heavy usage of menus. It is the best way to preserve most of the screen space available to display directory contents. Compared to other files managers, @{B2} does not have button panels. This will change in a next release as docks are planned using @{TM}.
A lot of people complained that @{B2} opens too many windows. Now, the directories have the @{" Auto-Iconify " link WindowOptionsSub} feature set by default. Then you will get new windows only when you open a new volume. Reset this option to @{" Keep Window " link WindowOptionsSub} if you prefer the old method which consists in opening a new window each time you open a directory.@{END2}
@{CHAP2 "Selecting files"}
File selection in @{B2} works like in Workbench. Selecting a file by default deselects all other selected files. To perform extended selection, you must hold the shift key while selecting files. See also @{" drag selection " link DragSelection}.
For those of you, lucky owners of a @{" 3 button mouse " link ThreeButtonMouse}, there is a special support in @{B2}.@{END2}
@{CHAP2 "Copying files"}
File copying works like Workbench too. Select your files, and while holding the left mouse button (LMB) pressed, release the shift key, drag the files over the target directory, and release the LMB. The @{" copy process " link CopyProcess} is run in the background leaving @{B2} available for other operations.@{END2}
@{CHAP2 "Current Directory"}
The notion of current directory is one of the most important things you must know about @{B2}. It is the base knowledge for a powerful usage.
The current directory only has meaning when running shell commands. Shell commands can be run either with the BrowserII/@{" Execute... " link ExecuteItem} menu item, or with a @{" user configured menu " link BrowserII.menu} in RUN or SHELL mode, or by doubleclicking on an executable file that has no associated icon. See the @{" Extract example " link CommonProblems} for an example usage of the current dir notion.
To quickly select a list of files, press the shift key, select the first file by pressing the left mouse button (LMB) over it, and then, without releasing the LMB, move the mouse over the other files. Reaching the bottom or the top of the window will scroll the list. Once the files are selected, you may then want to drag them over the target directory. Release the shift key (but not the LMB). The mouse pointer then change to a crosshair. Drag the mouse, and release the LMB.
There is another possible method to drag select files if you have a @{" 3 button mouse " link ThreeButtonMouse}. The MMB then replaces the shift key. It works the same way.
For lucky owners of a 3 button mouse, some goodies are available. For most of the features, the mid button acts like the shift key, so it may not conflict with utilities that do a MMB-Shift. By the way, some of those commodities are not programmed with care and may disable or conflict with some MMB features of @{B2}. You'll have to make a choice!
@{SUB2 "
"}Extended selection hitting MMB or LMB with MMB Pressed.@{END2}
@{SUB2 "
"}Pressing MMB then LMB enables drag selection.@{END2}
@{SUB2 "
"}MMB DoubleClick on a dir toggles @{" Auto-Iconify " link WindowOptionsSub} mode:@{END3}
@{SUB3 "
"}if AutoIconify is on, MMB DoubleClick opens a new window@{END3}
@{SUB3 "
"}if AutoIconify is off, MMB DoubleClick opens the new dir in the same window.@{END2}
@{SUB2 "
"}Dragging files with MMB toggles the copy/move mode.
Always Copy
is on, MMB always moves, else MMB always copies)@{END2}
@{SUB2 "
"}Pressing MMB & hitting the Close gadget closes all directories for the volume.@{END2}
@{SUB2 "
"}The same holds for the iconify gadget.@{END1}
@ENDNODE
@NODE CopyProcess "BrowserII.guide/Copy process"
@{START}
@{CHAP1 "Copy process"}
When copying files, @{B2} will check whether destination and one of the source concerned volumes are mounted, i.e. one of the source and destination volumes are simultaneously present in their drives (a diskette with a given volume name may not be in a drive).
When copying several files and/or directories, BrowserII always copy icons first, so that further Workbench directory scans will be faster.
If any source or destination volume is mounted (if you have only one drive for instance), @{B2} will use a maximum of 1024 KBytes for copy buffers if enough memory is available. This way, in order to copy some files from a diskette to another one, you don't need to go through the RAM Disk. Buffers are allocated during copy, and in any case @{B2} will not use more than 80% of the available memory at copy startup time for its buffers. This size of 1024 KBytes allows to copy a single DD diskette in a single step, even in PFS format.
If both destination and source directories are mounted, the buffer size will not exceed 512 KBytes.
@ENDNODE
@NODE MenusColors3.0 "BrowserII.guide/Note about menu colors with WB 3.0"
@{START}
@{CHAP1 "Note about menu colors with WB 3.0"}
For people who have AmigaOS 3.0 or 3.1 and have 8 or more colors in their Workbench Screen, you should read this note.
In WB 3.x preferences, you can edit the color pens of the screen's titlebar and menus. If you have a 8 or more color workbench, then you edit these pens using the MultiColored palette. If you don't use standard pens, (Black text on white background), and you run @{B2} in its own screen, you won't get the same colors for @{B2}'s menu. To get the same colors, you have to edit the pens in the system preferences in 4 color mode, since until now, @{B2} screen is a 4 color screen.
@{b}There are 2 independent preferences in the system for pens.@{ub}
Modifying the 4 color pens will not modify the layout of your 8+ color workbench, but will modify @{B2}'s.
This chapter summerize the most frequently asked questions.
@{SUB2 "
"}Extracting archives in a particular directory:
@{B2} comes with a shell script named
Extract
which detects the format of an archive and then calls the appropriate archiver to extract the archive. Usage of this script in @{B2} is straightforward. @{" Create a menu item " link BrowserII.menu} as follows:
@{CODE}ITEM {Z} Extract RUN Extract []@{BODY}
It is a good idea to use a shortcut for this menu item as it is often used. Here, it is Amiga-Z, or just
if you set your @{" SHORTCUTQUAL " link BrowserII.menu} to "".
Then select the archive to extract, activate the target directory window, and press Amiga-Z, or
. That's it!
See the @{" BrowserII.menu example " link //BrowserII.menu-example/Main} for a more featured Extract menu item.@{END2}
@{SUB2 "
"}Giving several arguments to a shell command that accepts only one:
Use the shell command @{" For " link For.doc/Main} included with @{B2}.
Example:
@{CODE}ITEM {Z} Extract RUN For [] DO Extract %%@{BODY}@{END1}
@{SUB2 "
"}The colors of my title bar is not the same as Workbenchs:
See @{" Menu colors under AmigaOS 3.0 " link MenusColors3.0}.
@ENDNODE
@NODE Tree "BrowserII.guide/Directory trees"
@{START}
@{CHAP1 "Directory trees"}
@{B2} can display a whole directory hierarchy in a single window. It has a finder-like layout, with little arrows allowing to fold directories. You can also @{" (un)fold all " link TreeSub} directories in a single keystroke. Scan is reasonably fast in @{" turbo mode " link WindowOptionsSub}, depending on the filesystem.
You can open trees with only the directories, or all directories and files. Note that you can open a tree with files and filter out files from display using the appropriate window filters settings. But opening a directory tree without files uses much less memory and system overhead.
Trees are not limited in the files and directories they can display. I could open a tree with files on a CDROM with 2000 directories and over 36000 files without problems. By the way, it used about 4 MBytes of RAM!@{END2}
@{CHAP2 "Opening Trees"}
@{SUB3 "
"}Tree with files:
Ctrl-Double-LMB
MMB-Double-LMB@{END3}
@{SUB3 "
"}Tree without files:
Shift-Ctrl-Double-LMB@{END2}
@{CHAP2 "Future"}
In a future release, it will be possible the convert a directory window into a tree window, using the @{" Window/Open/Make Tree " link OpenSub} menu. As only the first level directory will be read, subdirectory scan will be performed on directory unfold.@{END2}
@{CHAP2 "Selecting files in directory trees"}
Imagine the following directory structure:
@{CODE}include (dir)
dos (dir)
dos.h
dosextens.h
libraries (dir)
gadtools.h
iffparse.h
intuition.h@{BODY}
Selecting
iffparse.h
and dropping it in another directory would just copy it as usual. But now, select both
iffparse.h
and
include
, and drop them in the target directory. This will create the following structure:
@{CODE}include (dir)
libraries (dir)
iffparse.h@{BODY}
This makes it possible to copy only a part of a directory structure while keeping the structure.
When a directory in a tree is selected, two situations are possible:
@{SUB3 "
"}The directory contains selected subentries:
Then only the selected subentries will be processed on next action.@{END3}
@{B2} can automagically display the contents of an archive in a window, just like it was a normal directory. To make this feature functional, you must get the separate @{OA} package. @{B2} then mounts the archive and opens a directory or directory tree window (depending on the qualifiers used) just like for standards directories.
If you want to override this mechanism for some archive types (in case your have another better archive handler ;-), you can use an @{" autocmd " link Autocmds}. This also means that if you want an archive type to be supported by the @{OA} feature in @{B2}, you must remove the autocommand for this type.
@ENDNODE
@NODE Zoom "BrowserII.guide/Zoom"
@{START}
@{CHAP1 "Zoom"}
Zooming a window consists in showing as much information as possible about window contents. Priority is always given to height first. If it is not possible to display all files in one column, then @{B2} will attempt to display the less possible columns to show all files. If it is not possible within the bounds of the screen, window size will be rounded to the nearest width and height so there's no screen space lost.
Zoom can be performed automatically in response to some events in @{B2}. See the @{" AutoZoom " link AutoZoomSub} submenu in the @{" Window " link WindowMenu} menu.
It can also be performed upon user request: by a menu selection or shortcut or by the two zoom gadgets. These gadgets are invisible. The first one is the Zoom gadget and is the top half of the jauges, while the second one is the UnZoom gadget and is the bottom half of the jauges.
@{CHAP2 "Note"}
If you ask for a zoom while the directory to be zoomed is currently scanning, the zoom is deferred until the end of the scan.@{END2}
@{CHAP2 "Constraints"}
Window zoom can be size constrained.
@{SUB3 "
"}Maximum size:
If you don't want your windows to fill most of the screen, you may want to limit the maximum window size for a zoom operation. Maximum width and height can be set separately.@{END3}
@{SUB3 "
"}Minimum size:
Some of your windows are too small, or you want more columns ... capture a minimum window size.
Example:
You want your main window (the one with the device list) to be displayed with three columns, but you want it to be autozoom. Enlarge it to 3 columns manually or by using the @{" Window/Zoom/Wider " link ZoomSub} menu item, and snapshot the @{b}Min Width@{ub} of the window. Then the next zooms will keep at least the captured width, making the window wider and less high.
To capture the sizes of a window, use the @{" Window/Properties/Snapshot " link Snapshots} menu item. Whether a window has size contraints or not, the zoom window sizing methods explained before apply. In fact, the default size constraint of a window is the size of the screen.@{END3}
@{SUB3 "
"}Limiting the window size to the visible part of a virtual screen:
When you use @{B2} in a virtual screen, the zoomed windows may be larger than the size of the visible part of the screen. To prevent this, size a window to the size of the screens visible part, and @{" snapshot " link Snapshots} the window width and height as default for Directories, Trees, and Trees with files.@{END3}
@{SUB3 "
"}Overriding constraints:
Sometimes, you want to override the default contraints you set to window. To do that, control-click on the zoom gagdet of the window (hidden in the top half of the jauges). This will zoom the window with the screen size as bounds limits. As a more general usage, control-
overrides contraints. This is true for zoom function keys,...@{END3}
@{SUB3 "
"}@{b}Warning:@{ub}
Do not snapshot a default position or all windows will open at the same place!
@ENDNODE
@NODE Snapshots "BrowserII.guide/Snapshots"
@{START}
@{CHAP1 "Snapshots"}
The concept of window snapshot is well known as it exists in the Workbench. But window snapshot in @{B2} is even more powerful.
You can not only snapshot the size and position of the window, but also other local properties. Preferences may not be limited to the window, but to a whole volume, device, or as default preferences for all windows.
@{CHAP2 "Using snapshot"}
When asking for a window snapshot, a big requester appears, with lots of options. You are then prompted to select the information you want to freeze.
@{b}Important:@{ub}
You may save @{b}only the options that differ@{ub} from the default settings. When you open a window, @{B2} follows these rules to get window settings:
@{SUB3 "
"}Opening of a root directory:@{END4}
@{SUB4 "
"}Obtain default settings.@{END4}
@{SUB4 "
"}Obtain device settings that overrides previous ones.@{END4}
@{SUB4 "
"}Obtain volume settings that overrides previous ones.@{END4}
@{SUB4 "
"}Obtain directory settings that overrides previous ones.@{END3}
@{SUB3 "
"}Opening of a window subdirectory:@{END4}
@{SUB4 "
"}If the @{b}parent window@{ub} has the @{" local properties " link WindowOptionsSub} option set, the rule is the same as for root directories.@{END4}
@{SUB4 "
"}Else@{END5}
@{SUB5 "
"}Obtain settings of the parent directory.@{END5}
@{SUB5 "
"}Obtain directory settings that overrides previous ones.@{END3}
Example:
You may want to set default values for a particular device and/or volume so that each directory open relative to it, would get those settings. Then imagine you want to snapshot a particular directory on this volume. You should snapshot only the properties that differs from default values (checked by default). This way, if you change one of the volume defaults, even snapshotted directories will inherit the new defaults.@{END2}
@{CHAP2 "Snapshots databases"}
The snapshot files are created in @{B2}'s home directory, in the subdirectory
Snapshots
. They all have a file comment that summarizes their contents. So no data is written into the snapshotted directory. This won't fill your disks of annoying files, and allows to snapshot directories in write protected disks and CDROMs.
The default preferences for all windows (dirs, trees, alien and main window) are stored in
Snapshot-0
. All other files are numbered from 1 to ... There is one file for each device defaults (includes dir and trees defaults), and one file for each volume (includes dirs default, trees defaults, and local dir/trees snapshots).
The file comments then says for example
Snapshots for device DF0:
Note that volumes are remembered by name and datestamp. This makes it impossible to snapshot variable datestamp volumes, since they will always be identified as different volumes. This is the case for the RAM disk for example.
To remove a snapshot, you may
UnSnapshot
using the menu item in the Window/Properties submenu. Then, you get again the snapshot requester with, by default, the local directory snapshotted settings set.
If you did snapshot a directory that no more exists, you are not actually be able to remove it from @{B2}'s snapshot database. This will be possible with the future preference editor. The only way to remove old snapshots is to delete a snapshot file! It's not so silly, it's sometimes useful and easy.
@ENDNODE
@NODE Iconify "BrowserII.guide/Iconify"
@{START}
@{CHAP1 "Iconify"}
@{CHAP2 "@{B2} iconification"}
@{B2} can be iconified, so that it closes all its windows, and its screen if it has its own custom screen. However, there must not be any visitors window open in @{B2}'s custom screen, if any. Otherwise, it will complain about. But it is possible to iconify @{B2} while some background jobs are active. The status windows, if open, will be closed, and will continue to process silently.
To iconify @{B2}, hit the little arrow in the left border of the main window, just below the title bar. You can also activate the main window, and hit the
key.@{END2}
@{CHAP2 "Uniconifying @{B2}"}
Several methods are possible to uniconify @{B2}:
@{SUB3 "
"}Double click on its @{" AppIcon " link Running} if any.@{END3}
@{SUB3 "
"}Use its @{" hotkey " link Commodity}.@{END3}
@{SUB3 "
"}Use Commodities Exchange.@{END3}
@{SUB3 "
"}Run @{" BD " link ExternalCommandBD}.@{END2}
@{CHAP2 "Directory/Tree windows iconification"}
@{B2} directory and directory tree windows can be iconified too. Using window iconification, you keep directory contents in memory, thus preventing reading them again on next access.
To iconify a directory, hit the little arrow in the left border of the window, just below the close gadget, or hit the
key after activating the window. You can iconify all directories of the same volume by
shift iconifying
a window.
Once iconified, directories appear in the Alien window. Let's call the entries of the alien window @{i}icons@{ui}. The Alien Window can be open using F5 or menu
Window/Open/Alien Window
Icons are directories like any other directories in standard windows, that is to say they support all actions. You can select icons and release them over directories, you can also use icons as destination of a copy, or even rename or why not protect an icon.
@{b}Note@{ub}:
The Alien window is called
Alien
because it was intended to contain different kinds of entries such as leave-outs and aliases. At this moment, it is not yet implemented.
@ENDNODE
@NODE Network "BrowserII.guide/Network and MultiuserFileSystem support"
@{START}
@{CHAP1 "Network and MultiuserFileSystem support"}
@{B2} supports all multiuser/network packages that provides a standard accounts.library. This actually the case for Envoy, MultiUserFileSystem, and AS225.
This support means the ability to display file Owner/Group names, and protection bits, as well as modifing these attributes.
For display, select from the menu Window/File Infos, Protection, Owner, and Group. Protections bits are composed of owner bits, and, if
Group
is on, group protection bits as well as group name, and, if
Owner
is on,
others
protection bits as well as Owner name.
To modify protection bits, use the Set Protect action. To change owner, use Set Owner action.
@ENDNODE
@NODE Menus "BrowserII.guide/Menus"
@{START}
@{CHAP1 "Menus"}
@{SETTABS 40 75}
@{" BrowserII " link "BrowserIIMenu"} @{" Window " link "WindowMenu"} @{" Actions " link "ActionsMenu"}
@{" Update menus " link "UpdateMenusItem"} @{" Rescan " link "RescanItem"} @{" Rename " link "RenameItem"}
@{" Last Error " link "LastErrorItem"} @{" Open
" link "OpenSub"} @{" Make Dir " link "MakeDirItem"}
@{" Execute " link "ExecuteItem"} @{" Zoom
" link "ZoomSub"} @{" Duplicate " link "DuplicateItem"}
@{" Screen
" link "ScreenSub"} @{" Tree
" link "TreeSub"} @{" Set Date " link "SetDateItem"}
@{" Screen Font
" link "Fonts"} @{" Select Match " link "SelectMatchItem"} @{" Set Comment " link "SetCommentItem"}
@{" Window Font
" link "Fonts"} @{" Select All " link "SelectAllItem"} @{" Set Protect " link "SetProtectItem"}
@{" Run Mode
" link "RunModeSub"} @{" Filters
" link "FiltersSub"} @{" Set Owner " link "SetOwnerItem"}
@{" Copy Mode
" link "CopyModeSub"} @{" File Infos
" link "FileInfoSub"} @{" Add Icon " link "AddIconItem"}
@{" Copy Flags
" link "CopyFlagsSub"} @{" Sort By
" link "SortSub"} @{" Check Size " link "CheckSizeItem"}
@{" Device List
" link "DeviceListSub"} @{" AutoZoom
" link "AutoZoomSub"} @{" Information " link "InformationItem"}
@{" Options
" link "OptionsSub"} @{" Options
" link "WindowOptionsSub"} @{" Delete " link "DeleteItem"}
@{" Save Config
" link "SaveConfig"} @{" Properties
" link "PropertiesSub"}
@{" Quit " link "QuitItem"}
@ENDNODE
@NODE BrowserIIMenu "BrowserII.guide/Menu:
BrowserII
@{START}
@{CHAP1 "Menu: BrowserII"}
All the options set in this menu can be saved using the
Save Config
item. The options set in the
Window
menu are discussed later in this chapter.
@ENDNODE
@NODE UpdateMenusItem "BrowserII.guide/MenuItem:
BrowserII/Update Menus
@{START}
@{CHAP1 "Update Menus"}
Reloads the @{b}User Menus@{ub} @{" configuration file " link "BrowserII.menu"}.
@ENDNODE
@NODE LastErrorItem "BrowserII.guide/MenuItem:
BrowserII/Last Error"
@{START}
@{CHAP1 "Last Error"}
This will show you the last message which appeared in the screen title bar.
@ENDNODE
@NODE ExecuteItem "BrowserII.guide/MenuItem:
BrowserII/Execute...
@{START}
@{CHAP1 "Execute..."}
Pops up a requester allowing to enter a shell command. The command is initialised with the selected files (if any), else it will be the last executed command using this menu item.
@{b}Important@{ub}:
The command is executed in the directory of the active window. For example, entering the command
(silly! ;-), the output will be different depending on the active window.@{END1}
@ENDNODE
@NODE ScreenSub "BrowserII.guide/SubMenu:
BrowserII/Screen"
@{START}
@{CHAP1 "Screen Options"}
@{SUB 40 "Public Screen"}@{B2} opens its windows in the selected public screen@{END2}
@{SUB 40 "Custom Screen"}@{B2} opens its own screen (which is @{" public " link PublicScreen} too)@{END2}
@{SUB 40 "Workbench Colors"}Clones the colors of the Workbench screen.@{END2}
@{SUB 40 "Custom Colors"}Adjust colors with a color requester.@{END2}
@{SUB 40 "Backdrop pattern"}Install a grey pattern in the screen.@{END2}
pops up a requester showing the list of available public screens. If you plan to save this preference, you must choose a screen which is available each time you run @{B2}. Else, il will fall back to the Workbench screen. There is a special public screen which is called
frontmost
screen. Used in conjunction with a @{" hotkey " link Commodity}, @{B2} will popup in the current screen.
@ENDNODE
@NODE PublicScreen "BrowserII.guide/MenuItem:
BrowserII/Screen/Public Screen
@{START}
@{CHAP1 "Public Screen"}
@{B2}'s own screen is made public and is named
BrowserII
. Take care, public screen names are case-sensitive. For example, you can open a console in the @{B2} screen with the following syntax:
This console has deferred open (AUTO), will also have a close gadget (CLOSE), and will wait for you to hit close gadget before closing (WAIT). Note that if another public screen with the same name exists, @{B2} will name its screen BrowserII0, then BrowserII1,... (this can happen if you have the strange idea to run @{B2} twice!)
@ENDNODE
@NODE Fonts "BrowserII.guide/SubMenu:
BrowserII/Fonts
@{START}
@{CHAP1 "Fonts"}
@{SUB 40 "Default Font"}Use the defaut font@{END2}
@{SUB 40 "Custom Font"}Selects a special font for screen and or windows@{END2}
Proportional fonts are handled for both screen and window text.
@ENDNODE
@NODE RunModeSub "BrowserII.guide/SubMenu:
BrowserII/Run Mode
@{START}
@{CHAP1 "Run Mode"}
This submenu determine the mode to use to run the file you doubleclicked. If other files were selected at the time of the doubleclick, their names become parameters for the doubleclicked file.
If the file has an icon, and is not filtered out by an auto-command or mounted as an archive, it will automatically be run in Workbench mode.
Also note that @{B2} does a CD into the active window before running a command, whether you have doubleclicked on a file, or activated it through a menu selection. This is often @{b}very@{ub} useful.
@{SUB 40 "RunBack"}Run in background (input and output set to
)@{END2}
@{SUB 40 "Shell"}Use SHELLWIN console for program input/output@{END2}
@{SUB 40 "Request"}Pop up a requester to modify/confirm operation.@{END2}
@{SUB 40 "WBToFront"}Brings Workbench screen to front when running program.@{END2}
@ENDNODE
@NODE CopyModeSub "BrowserII.guide/SubMenu:
BrowserII/Copy Mode
@{START}
@{CHAP1 "Copy Mode"}
@{" Context " link ContextItem}
@{" Always Copy " link AlwaysCopyItem}
@{" Always Move " link AlwaysMoveItem}
@{" Link " link LinkItem}
@{" As... " link AsItem}
@{" Request " link CopyRequestItem}
@{" Update " link CopyUpdateItem}
@{" Don't overwrite files " link DontOverwriteFilesItem}
@{" Ask before Overwrite " link AskBeforeOverwriteItem}
@{" Backup replaced files " link BackupFilesItem}
@{" Copy Empty Dirs " link CopyEmptyDirsItem}
@{" Copy Hierarchy " link CopyHierarchyItem}
@ENDNODE
@NODE ContextItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Context
@{START}
@{CHAP1 "
Context
Copy Mode"}
If destination and source directory are located one the same volume, the file (or directory) will be moved. Else, it will be copied.
@ENDNODE
@NODE AlwaysCopyItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Always Copy
@{START}
@{CHAP1 "
Always Copy
Copy Mode"}
@{B2} will systematically make a copy of the file.
@ENDNODE
@NODE AlwaysMoveItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Always Move
@{START}
@{CHAP1 "
Always Move
Copy Mode"}
@{B2} will always move the file. If destination and source directory are on different volumes, the file will be copied to the destination directory and the source file deleted if the whole copy is successful.
@ENDNODE
@NODE LinkItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Link
@{START}
@{CHAP1 "
Copy Mode"}
Rather than copying/moving a file or directory, this will create a link. If destination and source directory are on different volumes, @{B2} will create a soft link, else, a hard link.
@{b}Note 1@{ub}:
Links are an advanced features of an operating system and should be used with care.@{END2}
@{b}Note 2@{ub}:
Soft links are not officialy supported by the actual AmigaOS (even 3.1). So, be prepared to encounter problems using some.
@ENDNODE
@NODE AsItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/[...] As...
@{START}
@{CHAP1 "
[...] As...
Copy Mode"}
As...
is an attribute for all previous choices in this submenu. If set, you will be prompted to enter a new file name for every files.
@ENDNODE
@NODE CopyRequestItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Request
@{START}
@{CHAP1 "
Request
Copy Mode"}
You'll asked if you want to move, move as, copy, copy as, or create a link before the drop operation takes place.
If you don't want to be requested each time you want to copy/move some files, you may use the Context or Always Copy or Always Move option. Then, if you want to perform a different operation as the default, your can press the Control key before dropping the files. This will force the request mode, and then allow to chose Copy As or Move As for example.
@ENDNODE
@NODE CopyUpdateItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Update
@{START}
@{CHAP1 "
Update
Copy Mode"}
@{B2} will copy the file only if the source file is more recent than the destination file, or if the destination file does not exist.
@{B2} will not overwrite an existing file. If there exists a destination file with the name you gave for the destination, the copy will not be performed.
@{B2} asks for confirmation before overwriting. This option is naturally mutually exclusive with the former one.
@ENDNODE
@NODE BackupFilesItem "BrowserII.guide/MenuItem:
BrowserII/Copy Mode/Backup Replaced Files
@{START}
@{CHAP1 "
Backup Replaced Files
Copy Mode"}
Each time a file to be copied/moved already exists, the existing file will be renamed to <oldname>~. If <oldname>~ already exists, it is deleted first.
This option will enable to recreate empty directories in the destination directory. It is particularly useful in its disabled mode, so empty directories are not copied.
You can store two prefered Device List configurations in you want. To switch between the two configurations, use the menu short cut. To edit the alternate configuration, select
Alternate
menu, and then set the preferences as usual. They will take effect immediately. The next time you
Alternate
, you will turn back to the other device list configuration, and so on...
The default configuration is the one which is active when you save your configuration. The other one is saved as
Alternate
@ENDNODE
@NODE OptionsSub "BrowserII.guide/SubMenu:
BrowserII/Options"
@{START}
@{CHAP1 "General Options"}
@{SUB 60 "Keep selected"}Keep the selected entries after an action@{END2}
@{SUB 60 "Toggle selections"}Clicking a selected entry deselects it.@{END2}
@{SUB 60 "ASynchronous actions"}Let this option ON. This is for debug purpose.@{END2}
@{SUB 60 "Open process status window"}Open an information window for copy, delete...@{END2}
@{SUB 60 "AutoCmds override icon's default tool"}Give priority to @{" AutoCmds " link AutoCmds} rather than default tool.@{END2}
@{SUB 60 "Use window font in requesters"}By default, requesters use screen font.@{END2}
@{SUB 60 "Quiet CheckSize"}Don't request at the end of Check Size action.@{END2}
@{SUB 60 "Display directory disk usage"}See @{" Jauges " link Jauges}.@{END2}
@{SUB 60 "Display proportion of visible data"}See @{" Jauges " link Jauges}.@{END2}
@ENDNODE
@NODE SaveConfig "BrowserII.guide/MenuItem:
BrowserII/Save Config
@{START}
@{CHAP1 "Save Config"}
Saves all options relative to first menu
BrowserII
, as well as the contents of the @{" select requester " link SelectRequester}.
@{b}Note to v2.x users@{ub}:
This no more saves preferences about the Current and Alien window. Use @{" snapshot " link Snapshots} for that.
@ENDNODE
@NODE QuitItem "BrowserII.guide/MenuItem:
BrowserII/Quit
@{START}
@{CHAP1 "Leaving @{B2}"}
We did not plan for implementing this option, but a few crazy guys screamed for it, so here it is... Anyway, you won't be surprised to read that you won't be able to quit @{B2} as long as one (or several) of the Asynchronous actions are still running, or if another application has a window open in @{B2}'s custom screen. By the way, @{" iconifying " link Iconify} @{B2} is possible while some actions are in progress.
@ENDNODE
@NODE WindowMenu "BrowserII.guide/Menu:
Window
@{START}
@{CHAP1 "Window Menu"}
All items and relative options in this menu are relative to the active (current) window. Some items are specialised to some kind of windows, and may be disabled depending on the active window.
@ENDNODE
@NODE RescanItem "BrowserII.guide/MenuItem:
Window/Rescan
@{START}
@{CHAP1 "Rescan"}
Rescans the content of the directory which corresponds to the active window. Since version 2.0, @{B2} scans directories asynchronously. You can iconify a directory while scanning. If you close a window while directory is being scanned, scan is aborted. Except for Alien Window that has no rescan method, this is valid for all other windows, including trees: the whole directory tree is rescanned.
@ENDNODE
@NODE OpenSub "BrowserII.guide/SubMenu:
Window/Open
@{START}
@{CHAP1 "Open SubMenu"}
@{SUB 40 "Open Parent"}Opens the parent directory of the active window (if any).@{END2}
@{SUB 40 "Open Dir..."}Open a directory by entering it's pathname, relative to current window. For example
to go back two levels.@{END2}
@{SUB 40 "Open Alien"}Opens the Alien Window which contains a listing of all @{" iconified " link Iconify} windows.@{END2}
@{SUB 40 "Open Status"}Opens the status window of all background processes.@{END2}
@{SUB 40 "Make Tree"}not yet implemented (Will convert a dir in tree window).@{END2}
@ENDNODE
@NODE ZoomSub "BrowserII.guide/SubMenu:
Window/Zoom
@{START}
@{CHAP1 "Zoom SubMenu"}
@{SUB 40 "UnZoom"}Sizes the window to it's smallest size.@{END2}
@{SUB 40 "Zoom All"}@{" Zoom " link Zoom} the window to show all files.@{END2}
@{SUB 40 "Zoom Dirs"}@{" Zoom " link Zoom} the window to show dirs only.@{END2}
@{SUB 40 "Taller"}Makes the window Taller.@{END2}
@{SUB 40 "Wider"}Display the window with one more column.@{END2}
@{SUB 40 "Thiner"}Remove a column but keep window height.@{END2}
@{SUB 40 "Show MaxSize"}Sizes window to its @{" maximum size " link Zoom}.@{END2}
@{SUB 40 "Show MinSize"}Sizes window to its @{" minimum size " link Zoom}.
@ENDNODE
@NODE TreeSub "BrowserII.guide/SubMenu:
Window/Tree
@{START}
@{CHAP1 "Tree SubMenu"}
@{SUB 40 "Fold All"}Folds all directories in a @{" tree window " link Tree}.@{END2}
@{SUB 40 "Unfold All"}Unfolds all directories in a tree window.
@ENDNODE
@NODE SelectMatchItem "BrowserII.guide/MenuItem:
Window/Select Match
@{START}
@{CHAP1 "Select Match"}
Opens the @{" selection requester " link SelectRequester}, and selects, in the current window, the entries matching the criteria you have given.
@ENDNODE
@NODE SelectAllItem "BrowserII.guide/MenuItem:
Window/Select All
@{START}
@{CHAP1 "Select All"}
Selects all entries in the active window!
@ENDNODE
@NODE FiltersSub "BrowserII.guide/SubMenu:
Window/Filters
@{START}
@{CHAP1 "Filters"}
Another important feature of @{B2}. Only the files which match the criteria you set will be displayed, but all will be counted (look at the information displayed at the bottom of the window).
@{SUB 40 "Set..."}Calls the filters requester.@{END2}
@{SUB 40 "No .info"}Hide .info files. This filter comes on top of the other filters.@{END2}
@{SUB 40 "Clear"}Removes all filters, all files and dirs will be visible.@{END2}
@{SUB 40 "Invert"}Reverses the action of all filters, so all visible files will be hidden and vice-versa. Useful for checking whether a file which you expect to be there has not been hidden through the action of one of the filters. In a directory tree, directories cannot be hidden.
@ENDNODE
@NODE FileInfoSub "BrowserII.guide/SubMenu:
Window/File Infos
@{START}
@{CHAP1 "File Infos"}
@{SUB 40 "Size in Bytes"}Show file size in bytes.@{END2}
@{SUB 40 "Size in blocks"}Show file size in blocks.@{END2}
@{SUB 40 "Protection"}Show protection bits. See @{" multiuser " Link Network} support.
@{B2} defines two more customs bits named C and L.
@{SUB 40 "Date"}Show file date in AmigaDOS format.@{END2}
@{SUB 40 "Time"}Show file time.@{END2}
@{SUB 40 "File Type"}Show @{" file type " link "whatis.library"}. Requires whatis.library.@{END2}
@{SUB 40 "Comment"}Show file comment.@{END2}
@{SUB 40 "Link"}Show link if file is a link. (Not if @{" Turbo Scan " link WindowOptionsSub} is on).@{END2}
@{SUB 40 "Drawer Arrow"}Put an arrow to the left of directories in tree windows.@{END2}
@{SUB 40 "Drawer Jauge"}Display a directory size jauge for each directory in trees.
@ENDNODE
@NODE SortSub "BrowserII.guide/SubMenu:
Window/Sort by
@{START}
@{CHAP1 "Sort"}
@{SUB 40 "Name"}Sort entries by name.@{END2}
@{SUB 40 "Date"}Sort entries by date/time.@{END2}
@{SUB 40 "Size"}Sort entries by size.@{END2}
@{SUB 40 "Entry Type"}Directories are displayed first.@{END2}
@{SUB 40 "File Type"}Sort by @{" file type " link whatis.library} and then by name/date/size.
@ENDNODE
@NODE AutoZoomSub "BrowserII.guide/SubMenu:
Window/Auto Zoom
@{START}
@{CHAP1 "Auto Zoom"}
This sub menu concerns the automatic @{" zoom " link Zoom} feature. When some events occurs, it is possible to automatically zoom a window. Just like everything in the
Windows
menu, these options are relative to the current window.
@{SUB 40 "Zoom All"}Maximum zoom at the end of the @{b}first@{ub} scan.@{END2}
@{SUB 40 "Zoom Dirs"}Like previous but show only directories.@{END2}
@{SUB 40 "Rescan"}Zoom window after each directory rescan.@{END2}
@{SUB 40 "Update"}Zoom window after copying/deleting files.@{END2}
@{SUB 40 "New File Infos"}Zoom window when changing file infos.@{END2}
@{SUB 40 "Tree Folding"}Zoom window when (un)folding dirs in a tree.@{END2}
@{SUB 40 "Only 1 Column"}Constraint the zoom to a single column.@{END2}
@{SUB 40 "Only if Zoomed"}Re-Zoom the window only if it was already before.
@ENDNODE
@NODE WindowOptionsSub "BrowserII.guide/SubMenu:
Window/Options
@{START}
@{CHAP1 "Window Options"}
@{SUB2 "
"}Find type by name@{ub}
The @{" file type " link whatis.library} is identified only by pattern matching on the filename. Fast but not very safe since names are not always meaningful for file types. (Requires whatis.library)@{END2}
@{SUB2 "
"}Find type by scan@{ub}
The @{" file type " link whatis.library} is not only identified by pattern matching but also by reading the first few bytes of the file. This is much more powerful than the previous option but slows down directory scan. (Requires whatis.library)@{END2}
@{SUB2 "
"}Turbo Scan@{ub}
Scans the directory using dos.library/ExAll() instead of Examine()/ExNext(). This is faster, and minimize disk trashing for concurrent accesses. I presume it should be even more faster on remote network directories. The dark side:
@{SUB3 "
"}You don't get size in blocks for files. (ExAll() limitation)
(So you get a computed size using size in bytes)@{END3}
@{SUB3 "
"}You don't get file types. (For speed condition).
Anyway, types are examined at doubleclick time.@{END3}
@{SUB3 "
"}Links are not recognized/read actually. This an AmigaDOS and/or FFS bug.
It may be fixed in a future release of the OS.@{END2}
@{SUB2 "
"}Keep Window@{ub}
A new window is opened when you doubleclick on a directory. This mode is forced if you SHIFT-doubleclick or MMB-doubleclick while the default
keep mode
Auto Iconify
Auto Close
.@{END2}
@{SUB2 "
"}Auto Iconify@{ub}
When you doubleclick on a subdirectory, the current directory is iconified and the new one is open in the same window. This mode is forced if you SHIFT-doubleclick or MMB-doubleclick while the default
keep mode
Keep Window
.@{END2}
@{SUB2 "
"}Auto Close@{ub}
When you doubleclick on a subdirectory, the current directory is flushed from memory and the new one is open in the same window.@{END2}
@{SUB2 "
"}Auto Disk Load@{ub}
@{b}This is not yet implemented.@{ub}
The window will be associated to a dos device such as DF0:, and will load the directory of the inserted disk in this device automatically.@{END2}
@{SUB2 "
"}Local Properties@{ub}
When set, this option prevents sub directories to inherit this directory properties. This is to be used in conjunction with @{" snapshots " link Snapshots}.
@ENDNODE
@NODE PropertiesSub "BrowserII.guide/SubMenu:
Window/Properties
@{START}
@{CHAP1 "Window Properties"}
The properties of a window are the set of local window attributes: Filters, File Infos, Sort, AutoZoom and Options.
@{SUB 40 "Copy"}Stores the properties of current window in an internal buffer for a later Paste operation.@{END2}
@{SUB 40 "Paste"}Pastes the last copied properties to the current window.@{END2}
@{SUB 40 "Affect Volume"}Copies the properties of the current window to all the windows belonging to the same volume.@{END2}
@{SUB 40 "Affect All"}Copies the properties of the current window to all the windows.@{END2}
@{SUB 40 "Restore Prefs"}Restores the @{" preferences " link Snapshots} for this window.@{END2}
@{SUB 40 "Snapshot"}Saves this window settings as @{" preferences... " link Snapshots}.@{END2}
@{SUB 40 "UnSnapshot"}UnSaves window preferences.
@ENDNODE
@NODE ActionsMenu "BrowserII.guide/Menu:
Actions
@{START}
@{CHAP1 "Actions"}
This menu gives access to all basic file operations, except drag and drop ones, ie copy/move/link. They are all executed in the background. This means that even when they pop up a requester, @{B2} is not busy. You can perform some other things if you need before answering the requester.
@ENDNODE
@NODE RenameItem "BrowserII.guide/MenuItem:
Actions/Rename
@{START}
@{CHAP1 "Rename"}
Renames the selected entries. If several entries are selected, you can rename them with jokers
la ARP
. If you are not familiar with this, exercise on some files of no value before using this action for good. For example, you can rename
mod.#?
#?.mod
, or more generally,
There is a
Capitalize
option, also available for
Copy As
and
Move As
operations which converts file names to lower case, except for the first letter to upper case. Useful when copying files from MSDOS disks.
@ENDNODE
@NODE MakeDirItem "BrowserII.guide/MenuItem:
Actions/Make Dir
@{START}
@{CHAP1 "Make Dir"}
Creates subdirectories in the active window. You can create several of them by separating names with spaces.
Example:
Work Games Work/Src
Warning:
Games Work/Src Work
would not be valid because you attempt to create a subdirectory of Work before having created Work itself.
@ENDNODE
@NODE DuplicateItem "BrowserII.guide/MenuItem:
Actions/Duplicate
@{START}
@{CHAP1 "Duplicate"}
Makes copy of file(s), you will be prompted for new names. The requester is the same as for @{" rename " link RenameItem}, and same rules apply.
@ENDNODE
@NODE SetDateItem "BrowserII.guide/MenuItem:
Actions/Set Date
@{START}
@{CHAP1 "Set Date"}
Changes the date stamp of the selected entry (entries) to the actual date. Since v2.20, date can be modified.
@ENDNODE
@NODE SetCommentItem "BrowserII.guide/MenuItem:
Actions/Set Comment
@{START}
@{CHAP1 "Set Comment"}
Modify/Create a file comment for the selected entries. If file already has a comment, it is displayed as default in the requester. File comments are limited to 80 characters.
@ENDNODE
@NODE SetProtectItem "BrowserII.guide/MenuItem:
Actions/Set Protect("
@{START}
@{CHAP1 "Set Protect"}
Change the protection bits of the selected entries.
You cannot set the pseudo C bit, as it is not real a protection bit, it just tells you that the selected entry has a comment. But you can reset it, this will delete the comment. Use with care, it is easy to get a lot of comments gone forever in no time.
The pseudo L bit is not available for the same reason.
You can also set the Other/Group protection bits but has no meaning outside a @{" multiuser/network " link Network} environment. FFS just ignores them.
@ENDNODE
@NODE SetOwnerItem "BrowserII.guide/MenuItem:
Actions/Set Owner
@{START}
@{CHAP1 "Set Owner"}
Changes the owner of the file. This has sense only within a @{" multiuser " link Network} or @{" network " link Network} environment. You must have the rights to do it. See your network/multiuser documentation.
(Requires accounts.library)
@ENDNODE
@NODE AddIconItem "BrowserII.guide/MenuItem:
Actions/Add Icon
@{START}
@{CHAP1 "Add Icon"}
Add an icon to selected file(s) and directories. The Icon is a default icon relative to the file type, and configured in whatis.library database. @{B2} will first search default icons in an assign ICONS:, and in standard ENV:Sys directory. The ICONS: is a workaround the prevent copying KBytes of default icons in ENV:Sys which is by default located in RAM:. The same rule apply to given separate shell command AddIcon.
Of course, requires whatis.library.
@ENDNODE
@NODE CheckSizeItem "BrowserII.guide/MenuItem:
Actions/Check Size
@{START}
@{CHAP1 "Check Size"}
Scans selected files and dirs to compute total size in bytes and blocks of all of them. If you choose to reselect entries, context of selection will be restored (including
Enter subdirs
) so that next action will be done on same files and dirs. Directories will get their size set. This way, it makes it possible, using rightmost main window @{" jauge " link Jauges}, to determine if a list of files and dirs will fit on destination volume.
In the menu BrowserII/Options, there is an option
Quiet CheckSize
which disable the requester at the end of the scan. Only directories then get their sizes updated.
@ENDNODE
@NODE InformationItem "BrowserII.guide/MenuItem:
Actions/Information
@{START}
@{CHAP1 "Information"}
Brings up Workbench's info requester. (AmigaDOS 3.0 and higher). Note that currently, workbench must be loaded or nothing will happen.
@ENDNODE
@NODE DeleteItem "BrowserII.guide/MenuItem:
Actions/Delete
@{START}
@{CHAP1 "Delete"}
Deletes the selected entries. You will (fortunately) be asked to confirm. If at least one directory is selected,
Delete
will delete only empty dirs, while
Delete All
will delete non-empty selected directories as well.
If the delete process encounters deletion protected files, you will be prompted if you want to override the protection.
@ENDNODE
@NODE Keyboard "BrowserII.guide/Mouse and Keyboard"
@{START}
@{CHAP1 "Mouse and Keyboard"}
@{CHAP2 "Function keys"}
@{SUB 22 "F1"}UnZoom current window.@{END3}
@{SUB 22 "F2"}Zoom current window to see all files and dirs.@{END3}
@{SUB 22 "F3"}Zoom current window to see all directories only.@{END3}
@{SUB 22 "F4"}Iconify current window, or @{B2} if main window is active.@{END3}
@{SUB 22 "F5"}Opens Alien Window.@{END3}
@{SUB 22 "F6"}Opens status window of processes currently running.@{END3}
@{SUB 22 "F7"}Folds all directories in a tree window@{END3}
@{SUB 22 "F8"}Unfolds all directories of a tree@{END3}
@{SUB 22 "S-F1"}Zoom taller@{END3}
@{SUB 22 "S-F2"}Zoom wider@{END3}
@{SUB 22 "S-F3"}Zoom thinner@{END3}
@{SUB 22 "ESC"}Pauses all processes and open their status window.@{END3}
@{SUB 22 "DEL"}Deletes selected files and directories@{END3}
@{SUB 22 "HELP"}Displays the about requester.@{END2}
@{CHAP2 "General mouse with qualifiers usage"}
@{SUB3 "
"}Pressing CTRL while selecting files forces Toggle-Select mode. This is important if you do not use the
Toggle Selections
option. This allow to de-select an entry without de-selecting all. I use this because the toggle-selections mode makes me turn mad! ;-)@{END3}
@{SUB3 "
"}Pressing CTRL for a zoom operations (gadgets & function keys) overrides zoom contraints.@{END3}
@{SUB3 "
"}Pressing SHIFT before dropping files toggles copy/move mode.@{END3}
@{SUB3 "
"}Pressing CTRL before dropping files forces the
Request
copy mode.@{END3}
@{SUB3 "
"}Shift-doubleclick on multiple assigns opens a list of assign components.@{END3}
@{SUB3 "
"}If you hold the shift key down while hitting a window close gadget, all windows belonging to directories of the same volume will be closed too, except iconified windows. If you want to get rid of iconified windows too, press CTRL key while closing the window.@{END3}
@{SUB3 "
"}Shift-doubleclick on directories toggles @{" auto-iconify " link WindowOptionsSub} mode.@{END3}
@{SUB3 "
"}Ctrl-doubleclick on directories/volumes open a @{" tree with files " link Tree}.@{END3}
@{SUB3 "
"}Shift-Ctrl-doubleclick on directories/volumes open a @{" tree without files " link Tree}.@{END3}
@{SUB3 "
"}See also @{" 3 button mouse support " link ThreeButtonMouse}.
@ENDNODE
@NODE Jauges "BrowserII.guide/Jauges"
@{START}
@{CHAP1 "Jauges"}
All windows but Alien have two jauges on their left border. The leftmost one always displays the disk percentage of occupied space. And the second one, to the right, displays the directory disk usage or the percentage of visible data depending on the option you choose (See menu BrowserII/Options).
@{SUB 11 "1."}Directory disk usage
If this option is selected, the rightmost jauge displays the proportion of used disk space used by this directory. For example, is you have a volume with no directories (all files are in the root directory), this jauge will say that the directory contains 100% of data present on this disk.@{END2}
@{SUB 11 "2."}Percentage of visible data.
If this option is selected, the rightmost jauge displays the proportion of visible data (in blocks) in this window. (If filters hide some entries of this dir, not all entries are visible!) This is useful for example when you hide .info files, a quick look at this jauge help you remembering that some files are not visible and you should not forget them.@{END2}
@{CHAP2 "Jauges of the main window"}
The leftmost jauge of main window is a copy of the same jauge of active window. If the active window is the main or alien, both main window jauges are empty.
The other jauge will help you to determine if selected files would fit on active volume (volume of active window) if a copy/duplicate operation would be performed. Imagine you want to copy some files on a floppy disk, and you don't know if there is enough free space on this disk for your selected files. You can examine informations in bottom border of windows of course but there is an easier way. Activate the destination window (without deselecting your files), and the second jauge of main window will tell you everything: The leftmost jauge shows the actual disk usage, and the other one what it will become after the copy. Then there is two possibilities. Your files fit on the disk: no problem. Or there's not enough free space: then, the second jauge shows of how much selected files exceeds disk space by displaying a dash (-). The jauge height always means the disk size.
@{b}Note@{ub}: Block size between source and destination volumes are assumed to be the same.
If you have installed the whatis.library, you'll be able to match files by type. If one or more positive file types are selected (without the exclude option), entries must match one of them. If no positive file types are selected, all files types are valid except excluded file types. For each file type, you can select associated subtypes.@{END2}
@{CHAP2 "Select Match"}
This requester is the same as precedent one, but with one gadget more,
Enter subdirs
. This enables you to virtually select files in selected directories.
As we say in french, a good example is better than a long speech. Suppose you want to clear archive bit of all files you have in a disk.
@{SUB 14 "1."}Open volume's window.@{END3}
@{SUB 14 "2."}Call Select Match.@{END3}
@{SUB 14 "3."}Put Files to ? and Dirs to N.@{END3}
@{SUB 14 "4."}Clear all protection bits and set A to +.@{END3}
@{SUB 14 "5."}Switch on "Enter subdirs".@{END3}
@{SUB 14 "6."}Validate the requester.@{END3}
Result: All files which have their archive bit set are selected, but any directories are selected since you set Dirs to N. Now:
@{SUB 14 "7."}Hold <Shift> key while selecting all dirs of this window.@{END3}
Each time you click left mouse button over a @{B2} window, if you @{b}don't@{ub} hold <Shift> at the same time, the file under the mouse pointer, if any, becomes selected, all others are deselected, and Enter subdirs bit is cleared. That is to say after each operation with enter subdirs, this option is reset (except if you always hold shift key), and must be set again if you want to do another action with this option.
Within actions with enter subdirs, if a directory pass through the filters, the action will take place also on the directory itself once it has been examined. But even if the directory doesn't pass through the filters, it will be entered, and files within this dir may be affected by the action.
This is a bit different for Copy action. If a directory doesn't pass through the filters, it won't be entered, and files within this dir will never be copied. But read carefully: Empty directories may be considered useless. So you can decide not to copy them by switching off this option. But Copy process is even more powerful. If for example, you decide not to copy empty dirs, if you copy a directory with enter subdirs and any entries of this dir pass through the filters, the directory will be considered as empty and won't be created in destination path. This makes it possible to make selective backups, without useless directories in destination volume.@{END1}
When attempting to copy (or move) a file over an already existing one, @{B2} will pop up a sophisticated requester. A lot of choices are then available, from the simple
Cancel
to more complicated options combinations.
The requester is composed of several parts: The buttons, the checkmarks, the string gadgets, and the requester text. The string gadgets are present only once
New Name
button has been pressed.
@{CHAP2 "Buttons"}
@{SUB 40 "Retry"}Retry operation (You may have changed checkmark states).@{END3}
@{SUB 40 "Open Dir"}Opens the directory where the problem happened.@{END3}
@{SUB 40 "Version"}Reads both files versions (using C:Version command).@{END3}
@{SUB 40 "Update"}Replace file only if newer than existing one.@{END3}
@{SUB 40 "Overwrite"}Overwrite the file.@{END3}
@{SUB 40 "NewName"}Enter new name for the file to create.@{END3}
@{SUB 40 "Skip"}Ignore the file and skip to next one.@{END3}
@{SUB 40 "Cancel"}Cancels the whole operation.@{END2}
@{CHAP2 "Checkmarks"}
@{SUB3 "
"}Backup replaced files
Backup replaced files
is checked, each existing file will be renamed to <oldname>~. If <oldname>~ already exists, it is deleted first.@{END3}
@{SUB3 "
"}Repeat action to all existing files
This option, when on, affects the following buttons:
Update
Overwrite
NewName
@{b}Beware@{ub}:
this option is on by default, thus selecting
will skip all existing files. You must remember to uncheck this option before hitting
if you want to perform a
by file
skip operation.
@{b}Note@{ub}:
NewName
to work with the
option, you must also perform a pattern rename. (Example:
#?.new
@ENDNODE
@NODE Commodity "BrowserII.guide/Commodity"
@{START}
@{CHAP1 "Commodity"}
@{B2} is a commodity. It supports the standard tooltypes:
@{SUB 30 "CX_POPUP"}(default is
) set to
FALSE
to start @{B2} in iconified state. Can be set in the (eventual) project icon in the SYS:WBStartup drawer.@{END2}
@{SUB 30 "CX_POPKEY"}(default is
control esc
)@{END2}
@{SUB 30 "CX_PRIORITY"}(default is 0)@{END2}
@{SUB 30 "CX_UNIQUE"}(default is
FALSE
) Set to YES or TRUE if you do not want to run BrowserII several times. If set to true, running BrowserII while it is already running will bring its screen to the front.@{END2}
There is a new mode for @{B2}'s screen which is the frontmost screen, if public. Used with hotkey, you can now pop up browser in the current screen when it is @{" iconified " link Iconify}, if you like to! Hitting hotkey while @{B2} is running but not iconified will bring its screen to front.
If Workbench is loaded when you start @{B2}, an @{" AppIcon " link Running} is installed. This icon can be used to uniconify @{B2}. You can also drop icons over it, and the corresponding directory will be open in @{B2}.
When @{B2} is used in Workbench screen, directory windows, as well as Alien and Devices windows are AppWindows. If you release an icon over a @{B2} window, the corresponding directory will be open in that window, and the preceding directory will be iconified.
An external command named BD is provided with @{B2}. This is an interface between shells and @{B2}. Running BD with no arguments will run @{B2} if it is not yet running, and make @{B2} open and scan your current shell directory. You can also specify one or more directories as argument to BD.
Note: @{B2} must be in your shell Path if it is not yet running.
BD can also be run from workbench. If you doubleclick on the Tool BD, @{B2} will open the directory containing BD. But you can also have project icons with BD as default Tool. In this case, if your project has no Tool-Types, the current dir will be open, otherwise, you can edit your project Tool-Types, and specify as many directories as you want. You should also specify in the BD Tool Tool-Types the full path to @{B2}, that is to say in which directory you have @{B2}.
In example given, @{B2} should be in SYS:Utilites directory.
You will best understand what follows if you have in front of you a printout of the @{" example config file " link //BrowserII.menu-example/Main} supplied.
A configuration file looks like a structured program. You should indent your lines to make the file as readable as possible.
The configuration file is named BrowserII.menu and must be in the same place as @{B2}.
The configuration file defines the menus you want, and what commands they will run. Comments begin with a #, and continue until the end of the line. Upper and lowercase do not make a difference.
@{CHAP3 "Keywords"}
@{SUB4 "
"}CMDWIN <console_name>
This will override the default console used for Command output which is
This should be placed anywhere in the file but better be at top of it. This console will in 2.0 have a close gadget, a deferred open, and wait for the user to hit the close gadget before closing the window. Under 2.0, if you use Command in Simple mode, you @{b}must@{ub} specify the WAIT option for your console, or it will close before you could read it.@{END4}
@{SUB4 "
"}SHELLWIN <console_name>
This will override the default console used for SHELL commands which is
@{CODE}
CON:0000/0011/0640/0100/Shell/Auto/Close/Wait
.@{BODY}
This should be placed anywhere in the file but better be at top of it.@{END4}
@{SUB4 "
"}SHORTCUTQUAL <qualifier string>
This can be used to add keys to access menus short-cuts. For example, you can use Left-Amiga, ALT, SHIFT or Ctrl. In fact useful values are
lcommand
(nothing). The first one allows the left amiga key to work as well as the standard right amiga key, while
allows to short cut menus with the single letter key. Any way, all commodities keywords are working, like:
lshift
rshift
lalt
ralt
control
...@{END4}
@{SUB4 "
"}COLOR <n>
This will set the foreground pen color for new items. You can change this as often as you want. The arguments is the pen number to use. The default is window detail pen.
This feature is active only under AmigaOS 2.x, as NewLookMenus of AmigaOS 3.x resets all the pens to system default values.@{END4}
@{SUB4 "
"}MENU <menu_name>
Creates a new menu. Each menu must have at least one item or submenu.@{END4}
@{SUB4 "
"}SUBMENU <submenu_name>
Creates a new submenu. Each submenu must have at least one item and can't have submenus. Each SUBMENU must end with an ENDSUBMENU.@{END4}
Defines a new menu item. Each item definition must have an <item_name> and an associated command. Each item is linked to the current menu or submenu. An ENDSUBMENU statement tells @{B2} to attach the next items to the current menu rather than to the current submenu. Any of the menu, submenu and item names may contain whitespaces. In this case, enclose the name in double quotes. A command character may be defined for the menu item by putting the character after the ITEM keyword and surroundinf it with {}'s.@{END4}
@{SUB4 "
"}KEY <hot key>
Allows more extensive short-cuts for menus. <hot key> is a commodities string, such as
control x
, or anything you want.@{END4}
@{SUB4 "
"}KEYTEXT <text>
(AmigaOS 3.x only)
Maybe be any text you want, but intended to help remember menu extended short-cuts. You may for example use KEYTEXT
for previous KEY
control x
. This text will be right aligned in the menu strip.@{END4}
@{SUB4 "
"}WBTF
Brings workbench to front just after running the command.@{END4}
@{SUB4 "
"}REQUEST
Opens a requester enabling you to modify the command before running it. Not available for WB mode.@{END3}
Command syntax is described below.@{END4}
@{SUB4 "
"}<command_def>
Programs can be run in three ways: RUN, SHELL, and WB. For all modes, STACK and PRI are optional. If STACK is less than 4000 bytes, or if no stack is specified, the stack will be set to the ParM's task stack. That is to say the stack size at the time ParM was run. There's an exception: If ParM is resident, ParM stack will always be 4000 bytes.
This mode creates a background shell. This mode should be used for scripts. If the bit s of your script file is set, it is automatically sourced (No need for the execute command). Redirection can be done in this mode. You can specify several commands separated with semicolons (;). If you want selected files to be passed as arguments, you may place square brackets [] at insertion position.
There is an alternative to get arguments with a full pathname, rather than a path relative to the current directory (active window). Just put [:] instead of [] in the command line.
But be warned. In most cases, @{b}this is not necessary@{ub}, and dangerous! Because volume names may not be unique, files passed as parameters may not be the ones you selected. Current directory is a lock and @{b}is@{ub} unique. Anyway, it can be useful when giving file names to an already loaded running process with a current dir different from the selected files' directory. For example, you get two ARexx examples in this archive that need full path arguments, View.adpro and DeliPlay.rexx.
There is another drawback: arguments have longer names, and as a command line is limited to 512 bytes, you cannot give as many arguments to a command as with a current-dir relative path.@{END5}
This mode now does the same as RUN, but if no window is given, the default shell window is taken.@{END5}
@{SUB 20 "3)"}WB syntax
@{CODE}WB [STACK n] [PRI n] command@{BODY}
@{CODE}WB [STACK n] [PRI n] command []@{BODY}
with the second version taking arguments
Executes command in Workbench mode. To get arguments, add [] to the command. Warning: If STACK is specified here, it will override the stack specified in the icon of the command. Your command may crash if you ask a smaller stack than in the icon. Do it at your own risk.@{END4}
@{SUB4 "
"}BARLABEL
Adds a bar between last item and next one.@{END3}
For all modes but WB, your command is searched first in the resident list and then in the CLI path at the time ParM was run. To know the path in which ParM searches its commands, just issue the Path command in the requester of ParM Command command, or open a NewCLI or Shell from ParM and issue the Path command.
A config file is given as an example.@{END2}
@{CHAP2 "Limitations"}
If a command in RUN or SHELL mode can't be started, you will never know, except you won't see it working.@{END2}
@{CHAP2 "Known bugs"}
See notes for external commands.
RUN PRI 1 NewShell
does not work. Pri is always 0. Not a ParM bug.@{END2}
@{CHAP2 "Tutorial"}
Now you've read about all ParM is able to do, I think you'd like to know which mode you should use to run your favorite tools.
First, when you want to add a menu item, you should know:
@{SUB 14 "1)"}Does your tool support workbench run?@{END3}
@{SUB 14 "2)"}Do you want your tool to inherit ParM's current dir, or have its own?@{END3}
@{SUB 14 "3)"}Do you want your tool to inherit ParM's CLI Path?@{END3}
@{SUB 14 "4)"}Do you want your tool to use a console window for its output?@{END3}
SHELL mode is now the same as RUN but with a default console if not specified. So, the choice between RUN and WB is easy. If you need a console or the Path, use RUN mode. Else, you can use WB mode.
You can run commands using hot keys. But @{B2} is not a background commodity to run or pop up various utilities. Use special tools to do that such as Yak, or others. Hot keys in @{B2} are active only when a Browser window is active. In fact, hot keys are configured as menu short cuts, so you may consult @{" menu configuration " link BrowserII.menu}, especialy the KEY and KEYTEXT keywords.
@ENDNODE
@NODE AutoCmds "BrowserII.guide/Auto Commands"
@{START}
@{CHAP1 "Auto Commands"}
AutoCommands are commands that are run when you double click on a file depending on the file type. File types are recognised by @{" whatis.library " link whatis.library} so this feature is available only if you have it in your system.
File types configuration is done via @{" whatis.library " link whatis.library} configuration.
AUTOCMDs are configured in the @{" BrowserII.menu" link BrowserII.menu} file with the following syntax:
@{SUB 35 "<file type>"}The file type name (you can see it by setting
File Infos/File Type
(i.e:
, etc...)@{END2}
@{SUB 35 "<run mode>"}Same as for @{" menu items " link BrowserII.menu} (WB, RUN,...)@{END2}
@{SUB 35 "<command>"}The command you want to execute for this type of file. Same syntax as @{B2}'s @{" menu items " link BrowserII.menu}.@{END2}
@{SUB 35 "WITHSUBTYPES"}AUTOCMD is inherited by subtypes of the type given. If an AUTOCMD exists for a subtype of the given type, it takes precedence over it.@{END2}
Examples:@{CLEARTABS}
AUTOCMD "Text" WITHSUBTYPES WBTF RUN More []
AUTOCMD "Source C" RUN Ed []
If you doubleclick on a file and this file is a text file but not C Source file (which is a subtype of Text) then
will be run with the file as argument. If you DoubleClick on a C Source file, then
will be run instead of
It is strongly recommended to have a look at the complete example given in BrowserII.menu. The file is easy to understand.
@ENDNODE
@NODE whatis.library "BrowserII.guide/File types and whatis.library"
@{START}
@{CHAP1 "File types and whatis.library"}
This library is responsible of file type identification in @{B2}. It now quite know as some other PD software uses it.
The whatis.library comes as a separate package, even though the library itself and a simple configuration file comes with it. The complete distribution can be downloaded from aminet, and makes part of our install disk.
Read the @{" whatis.library documentation " link "whatis.doc/Main"} for more information about configuration.
@ENDNODE
@NODE "Changes" "BrowserII.guide/Changes"
@{START}
@{CHAP1 "Changes from versions 2.x"}
@{CHAP2 "BrowserII.menu"}
The menus configuration file
S:BrowserII.menu
has moved to @{B2}'s home directory. The installation script detects an existing file in S: and moves it to the new location of @{B2}.
The crappy ACTIVATEKEY has gone from BrowserII.menu (and ParM.cfg). You must remove it. It has definitely been made obsolete by CX_POPKEY.
You must modify your SHORTCUTQUAL (if any). It now uses commodities syntax. For
left Amiga
key to work as well as standard right amiga for menu shortcuts:
@{CODE}SHORTCUTQUAL "lcommand"@{BODY}
For direct shortcuts (without any qualifier):
@{CODE}SHORTCUTQUAL ""@{BODY}
Browser now requires that each command (either RUN, SHELL or WB) that may take arguments include square brakets [] or [:] where to insert arguments. Commands that don't have [] won't have selected files passed as arguments, and selected files won't be unselected once the command has been run.@{END2}
@{CHAP2 "Save Config"}
The config file DEVS:BrowserII.cfg has also moved to the same location. Although the file format has changed, you will start back from default options when first installing version 3 of @{B2}.
This way, @{B2} has now all its files in a single directory, making easier copying, and ready to use floppy disk based installation.
Note that now, @{" Save Config " link SaveConfigItem} only saves the attributes set in the
Some global window attributes are now local to each window such as autozoom features for example.
These attributes are no more saved with the @{" Save Config " link SaveConfigItem} menus. You must now use the @{" Window/Properties/Snapshot " link Snapshots} menu item, which allow to save the active window properties as local or default configuration.@{END2}
@{CHAP2 "Note to those who had beta 2.9 versions"}
The MMB-doubleclick feature is back to it's original 2.41 function which is
toggle Auto-Iconify
feature. Directory tree opening is now available with Control-doubleclick or MMB-Double-LMB, because in fact, auto iconify it is much used than opening directory trees, and it's easier this way.@{END2}
See the @{" release notes " link "Release Notes"} for new features.
Moving a device over another device calls SYS:System/DiskCopy, and Duplicate a single device too.
CLI arguments are now quoted only when needed.
A lot of little invisible improvements.@{END2}
@{SUB 15 "1.11"}Bug fixes.
With parm.library 3.4 and higher, RUN modes work under 2.0.@{END2}
@{SUB 15 "2.0"}New features:
Iconification, zoom, jauges, Workbench 2.0 look (under 2.0), parametrable fonts, asynchronous dir scan, and bug fixes.
External command BD.@{END2}
@{SUB 15 "2.03"}Minor bug fix.@{END2}
@{SUB 15 "2.04"}
Copy->Move
bug fix. (won't delete source file)@{END2}
@{SUB 15 "2.05"}Bug Fix: A CurrentDir() was missing which can cause crash, bug in copy when skipping big file. Removed trash of prop gadget with autozoom under 2.0@{END2}
@{SUB 15 "2.10"}29.5.1992
Optional whatis capability: recognize some files (ILBM, PPDATA, doc,...), You can define new type (see docs of whatis.library).
Auto command (custom command for each filetype ).
@{B2} can work without whatis.library.
AddIcon and CheckSize action added, Back pattern option added (KS2.x only), should be custom in future.
Optional automatic main window Zoom.
Optional save Main window size/position
BD has now 3 new option.@{END2}
@{SUB 15 "2.11"}RunMode was not printed in GetString() title bar when double clicking on a file. fixed.
When changing Sort mode for a window, window was not updated. fixed.@{END2}
@{SUB 15 "2.12"}RunMode on doubleclick was always Shell with WB 2.0. fixed.
After closing a window, check-marks for new current window was not udated. fixed.
WBToFront now supported for WBRun too.
A TAG_DONE was missing for backdrop window open (Pattern Option)
@{b}This was the last KickStart 1.3 version!@{ub}@{END2}
@{SUB 15 "2.20"}For KS 2.0 only, sorry.
arp and req libraries no more needed.
New lovely requesters (Underscored chars are shortcuts).
Bold gadget is default response (Return key).
ESC cancels all requesters.
Processes status windows.
New screen modes available.
Virtual autoscroll screens.
New wonderful Select/Filters requester with file types criteria.
New look in menus.
FileInfo options for alien window entries saved in config file.
OpenDir done relative to current dir (enables opening of
for example)
ShortCuts available when pattern's backdrop window is active.
@{B2} can be iconified even when processes are running.
Touch action changed in SetDate (like AmigaDOS command). You can then modify the date.
Added new internal protection bit L to identify links.
Saving Size/Position of main and alien windows made easier.@{END2}
@{SUB 15 "2.21"}No more truncates french dates.
Works fine with 4000 bytes of stack. (2.20 needed 4500 bytes).
Uses new asl.library V38 screen mode requester.@{END2}
@{SUB 15 "2.22"}New look menus under AmigaDOS 3.0.
New action
WB Info
under AmigaDOS 3.0.
Bug fix: Mem jauge layout was not correctly handled under V39.
Backdrop pattern now implemented as a layer hook, and no more uses precious chip memory.@{END2}
@{SUB 15 "2.23"}Bug fix. Replaced ExNext() with MatchNext() to fix problems with new V39 DirCache FileSystem.@{END2}
@{SUB 15 "2.30"}Localized.
Screen's bitmap made Interleaved under 3.0 (scrolling much nicer)
Bug fix in WB Info. Did not handle properly .info files.
You can now run a tool by doubleclicking on it's icon. Makes it possible to run projects made of only an icon (for example: clicking on English.info to run software install in english).
Uses system busy pointer under WB3.0.
Bug fix in LoadConfig(). Config revisions were not properly handled.@{END2}
@{SUB 15 "2.31"}Pooled memory under WB3.0
@{B2}'s screen now inherits Workbench3.0's properties. (Your prefered pens,...) See note about pens for 3.0 users.@{END2}
@{SUB 15 "2.32"}Fixed a MungWall hit.
Added
Keep Window
features, asked by Gilles Soulet.@{END2}
@{SUB 15 "2.33"}Bug Fixes. Files where not unghosted on unmounted volumes.
Memory pools semaphore protected.
Deleting directories in RAM: was not possible under V37 since version 2.23 (due to modif for DCFS). Worked under V39. Fixed.@{END2}
@{SUB 15 "2.34"}Pooled memory under all system versions, including 2.0!@{END2}
@{SUB 15 "2.36"}Deleting links to dirs no more deletes dir contents. Only the link is removed.
Added
Update
button when asking before overwriting a file.
now opens file's parent dir.
Added Affect Volume possibility.
You can now make a directory (MakeDir) with an icon.
Turbo directory scan.@{END2}
@{SUB 15 "2.37"}Drag Selection. (release Shift key to copy/move files).
Menus available when backdrop window is active.
Keep modes now keep the same window rather than opening a new one and then closing parent.@{END2}
@{SUB 15 "2.38"}Middle button handling.
New request mode for copying/moving files (Copy Mode/Request)
Colors saved in 32 bits under V39 for AGA machines. This is useful only if you edit the palette with a special utility. We'll soon release a palette.library which will edit colors in 24 bits, using the colorwheel.
Command line length increased to 512. (You can select more files for External Commands in RUN/SHELL mode).
Added an AppIcon in Workbench.@{END2}
@{SUB 15 "2.39"}AppWindows. (See @{" Workbench Support " Link "WorkbenchSupport"}).
Keeps window size after checksize. (will become optional)
Enhanced (faster) scrolling for big windows.
Added a safety check. If you drag a file and you release it less than 350 ms after selecting it, you will be asked a confirmation for the copy/move operation. You must be a zombie to be faster!
Arrows associated with scrollbar. Not yet functional.
Another bug fix in LoadConfig().@{END2}
@{SUB 15 "2.40"}New iconify gadget image.
Page scrolling (jump) now keeps one common entry between pages.
Scrolling with new arrows.
Menu layout no more locks backgroung actions when status windows are open.
When started from WB, @{B2}'s process get a copy of the WB path, just like if it were started from a shell.
Scrolling support in drag-selection.
Added
to get full path arguments.
Pressing MMB while holding LMB no more forces toggle-selection.
Uses palette.library under V39 if available.
Better window placement for big screens.
Added Doc for CTRL key usage. (never been documented before!)
Bug fix in realtime scroll. (window top and/or bottom borders might be trashed).
Fixed several bugs WB Info.
Various other optimisations/bug fixes.
Code cleanup.@{END2}
@{SUB 15 "2.41"}Little fixes.
Bumped revision because a lot of 2.40 beta were distributed.@{END2}
@{SUB 15 "2.42"}(Not released)
Modification of the about requester for registered users.
Support for different kinds of assigns in the device list.
Support for Multiple Assings.
Standard Assigns are now unique. If you have an assign and a volume with the same names and you doubleclick on the assign, you'll get the assign directory, not the volume. This is also true when you drop files over an assign.
@{B2} may now run on any public screen. Not only Workbench.@{END2}
@{SUB 15 "2.43"}(Not released)
Keep prop gadget position between directory rescan.@{END2}
@{SUB 15 "2.44"}(Not released)
Jauges a bit wider under SuperHires screen modes.
New standard 3D scrollbars
Delete & Write protection bits no more copied.@{END2}
@{SUB 15 "2.9"}3.0 pre-release. Reserved to beta testers.@{END2}
@{SUB 15 "3.0"}Directory tree.
Window snapshots.
File comments display.
Links support and display.
Network/MultiuserFileSystem support.
Archive support (Get separate @{OA} package)
Proportional font in windows.
Improved device list display.
Delete when dropping files out of a window.
Deletion of delete-protected files request
Extended menu shortcuts (some kind of hot keys).
Enhanced actions and copy requesters.
Now a commodity (can start in iconified state)
Finds default tools in path.
Removed the title bar memory jauge. Use TitleClock or other.
And more!...@{END2}
@{SUB 15 "3.01"}Added CX_UNIQUE tooltype.
Deferred ScanDevs()
Shilt-Alt-Close_Window replaced by easier Ctrl-Close
Background image (under 3.x only) (code by Walter D
rwald)@{END2}
@{SUB 15 "3.02"}Improved Background image display speed. (Walter D
rwald)
Changed NOAPPICON tooltype to APPICON=<filename>
Move As
on same volume was not working!!
New guide (AmigaOS 3.1 and above only)
New set of MagicWB icons. Thanks again Walter!
Added all available tooltypes in icons as comments.
New Italian & Spanish catalogs.
Linked with fixed pools.lib from Mike Sinz.@{END2}
@{SUB 15 "3.03"}Fixed bugs/enforcer hits in date decoding (select requester).
Added support for Lzx in
Extract
script.
Added missing information for copy process in guide file.@{END2}
@{b}Pierre CARRETTE died in a motorbike accident on 12 May 1995.@{ub}
@{SUB 15 "3.04"}1995 06 04
Internal.
add the tooltype CFG_ShowSizeInByte@{END2}
@{SUB 15 "3.05"}1995 06 10
Internal.
fix enforcer-hit when deleting soft-link on file.@{END2}
@{SUB 15 "3.06"}1995 06 11
Internal.
fix little memory loss. (about 200 byte)@{END2}
@{SUB 15 "3.09"}1995 09 17
Internal.
FileName with maximum (=32 char) lenght make lots of gfx garbage. fixed.@{END2}
The next step in @{B2} is a separate preferences editor for lots of new options, color settings, menus, auto-commands, and ... docks! We plan to use the toolmanager.library for this feature. This version has some new features hidden, disabled, or not finished because I'm a bit fed up with @{B2}, after more than one year working on the same tool. Don't blame me please! Anyway, I will try to make more regular updates than before, mainly on Aminet.
@ENDNODE
@NODE "Updates" "BrowserII.guide/Updates"
@{START}
@{CHAP1 "Updates"}
To get the latest version of @{B2}, download it from an AmiNet site in directory util/dir. If you do not have access to AmiNet, you'll then have to wait for Fred Fish disks/CDROMs, or other diskette collections.
@ENDNODE
@NODE "Copyright" "BrowserII.guide/Copyright"
@{START}
@{CHAP1 "Copyright"}
@{B2} is copyrighted by @{b}Sylvain ROUGIER@{ub} and @{b}Pierre CARRETTE@{ub}. It may not be sold in or together with commercial software without written approval by the authors. It may be freely distributed on usual Fish disks and CDROMs, Aminet servers and CDROMs, Pearl, CAM, ... It cannot be made available for downloading from a server which is a commercial operation. The general principle is that it is forbidden to make a profit through the use or distribution of this program without our written consent.
Distribution by
France Festival Distribution
after any sort of translation is definitely @{b}illegal@{ub}.
@{B2} is shareware. If you use it consistently, you ought to send us a contribution or your conscience will itch. Shareware fee is $25. You will then get a so called key file, which will stay valid for long time. You will continue to get updates from usual fish disks and aminet download.
When you are not registered, the About requester appears from time to time. To become a registered user, fill in the @{" Registration Form " LINK "Registration Form/Main"} and send it to the address below. If you have an email, we will be able to send you your keyfile very fast.
Send registration order form to (except U.S. users):
@{SUB2 ""}Sylvain ROUGIER
39 rue Carnot
86000 Poitiers
France
EMail: rougier@ss3.univ-poitiers.fr
IRC on channel #AmigaFr: Nickname "Un"@{END2}
North American registration and support site for BrowserII is now available from:
@{SUB2 ""}Jon Peterson
P.O. Box 2661
San Angelo, TX 76902
EMail:
@{SUB 25 "FidoNet:"}1:383/25 or 26 or 30@{END3}
@{SUB 25 "InterNet:"}jon.peterson@twisted.com
j.peterson22@genie.geis.com@{END2}
You can always FREQ the latest versions of and BrowserII at
Dark Knights (915)944-9283 in the Amiga files section as
BrowserII_v3.lha.
@ENDNODE
@NODE "Bug reports" "BrowserII.guide/Bug reports"
@{START}
@{CHAP1 "Bug reports"}
If you have internet access, the best way to send bug reports and enhancement requests is to send e-mail to:
rougier@ss3.univ-poitiers.fr (Sylvain ROUGIER)
Otherwise, send it by postmail to @{" Sylvain ROUGIER " LINK "Registration"}.
Several people reported troubles with MFS & CrossDos. It sometimes happened that closing a PCx: directory while removing an MSDOS disk crash the machine with old version of CrossDos. With version 40.19 of CrossDosFileSystem, this bug has gone.
This definitely is *not* a bug of BrowserII.
If you encounter a bug we can't reproduce, please send us a bootable floppy disk and describe how to get it.
You will in turn get a free registration for BrowserII.
rwald for creating a set of MagicWB icons, new nice formatted guide, and screen backfill hook with datatypes image loading.
Cedric Beust, Philippe Brand, Gilles Soulet, Ga
l Marziou, Jean-Baptiste Yunes, Eric Totel, Olaf Gschweng, Alessandro Galassi, and all other translators, registered users, and beta testers.
And to my friend Pierre CARRETTE
@ENDNODE
@NODE "Disclaimer" "BrowserII.guide/Disclaimer"
@{START}
@{CHAP1 "Disclaimer"}
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDER AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THEIR COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
(.txt)